Dec 03 01:47:36.024 INFO testing metric-0.1.2 against master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61 for beta-1.31-5
Dec 03 01:47:36.024 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-0/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 03 01:47:36.534 INFO [stdout] 89c4589d031e2adb2da9f0923431a49189f98275e6f5cf3e3341c2e52bc637d0
Dec 03 01:47:36.536 INFO running `"docker" "start" "-a" "89c4589d031e2adb2da9f0923431a49189f98275e6f5cf3e3341c2e52bc637d0"`
Dec 03 01:47:38.496 INFO [stderr] usermod: no changes
Dec 03 01:47:38.543 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 03 01:47:38.543 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 03 01:47:38.543 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 01:47:38.544 INFO [stderr] files will be included as a benchmark target:
Dec 03 01:47:38.544 INFO [stderr] 
Dec 03 01:47:38.544 INFO [stderr] * /source/benches/nbody_raw.rs
Dec 03 01:47:38.544 INFO [stderr] * /source/benches/nbody_uom.rs
Dec 03 01:47:38.544 INFO [stderr] * /source/benches/nbody_metric.rs
Dec 03 01:47:38.544 INFO [stderr] * /source/benches/nbody_dimensioned.rs
Dec 03 01:47:38.544 INFO [stderr] 
Dec 03 01:47:38.544 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 01:47:38.544 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 03 01:47:38.544 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 03 01:47:38.544 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 01:47:38.544 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 01:47:38.544 INFO [stderr] 
Dec 03 01:47:38.544 INFO [stderr] For more information on this warning you can consult
Dec 03 01:47:38.544 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 01:47:38.571 INFO [stderr]    Compiling metric v0.1.2 (/source)
Dec 03 01:47:44.127 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 5.60s
Dec 03 01:47:44.147 INFO [stderr] su: No module specific data is present
Dec 03 01:47:45.179 INFO running `"docker" "inspect" "89c4589d031e2adb2da9f0923431a49189f98275e6f5cf3e3341c2e52bc637d0"`
Dec 03 01:47:45.485 INFO running `"docker" "rm" "-f" "89c4589d031e2adb2da9f0923431a49189f98275e6f5cf3e3341c2e52bc637d0"`
Dec 03 01:47:45.887 INFO [stdout] 89c4589d031e2adb2da9f0923431a49189f98275e6f5cf3e3341c2e52bc637d0
Dec 03 01:47:45.893 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-0/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 03 01:47:46.339 INFO [stdout] e72b19aeec770662aab2f674f5efde3f124bd3c98203640625b8b23d00a3a433
Dec 03 01:47:46.339 INFO running `"docker" "start" "-a" "e72b19aeec770662aab2f674f5efde3f124bd3c98203640625b8b23d00a3a433"`
Dec 03 01:47:47.566 INFO [stderr] usermod: no changes
Dec 03 01:47:47.636 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 03 01:47:47.636 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 03 01:47:47.636 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 01:47:47.636 INFO [stderr] files will be included as a benchmark target:
Dec 03 01:47:47.636 INFO [stderr] 
Dec 03 01:47:47.636 INFO [stderr] * /source/benches/nbody_raw.rs
Dec 03 01:47:47.636 INFO [stderr] * /source/benches/nbody_uom.rs
Dec 03 01:47:47.636 INFO [stderr] * /source/benches/nbody_metric.rs
Dec 03 01:47:47.636 INFO [stderr] * /source/benches/nbody_dimensioned.rs
Dec 03 01:47:47.636 INFO [stderr] 
Dec 03 01:47:47.636 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 01:47:47.636 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 03 01:47:47.636 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 03 01:47:47.636 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 01:47:47.636 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 01:47:47.636 INFO [stderr] 
Dec 03 01:47:47.636 INFO [stderr] For more information on this warning you can consult
Dec 03 01:47:47.636 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 01:47:47.654 INFO [stderr]    Compiling nodrop v0.1.13
Dec 03 01:47:47.663 INFO [stderr]    Compiling dimensioned v0.6.0
Dec 03 01:47:47.667 INFO [stderr]    Compiling uom v0.14.0
Dec 03 01:47:49.548 INFO [stderr]    Compiling generic-array v0.5.1
Dec 03 01:48:02.947 INFO [stderr]    Compiling metric v0.1.2 (/source)
Dec 03 01:48:08.637 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 21.04s
Dec 03 01:48:08.644 INFO [stderr] su: No module specific data is present
Dec 03 01:48:08.887 INFO running `"docker" "inspect" "e72b19aeec770662aab2f674f5efde3f124bd3c98203640625b8b23d00a3a433"`
Dec 03 01:48:08.967 INFO running `"docker" "rm" "-f" "e72b19aeec770662aab2f674f5efde3f124bd3c98203640625b8b23d00a3a433"`
Dec 03 01:48:09.122 INFO [stdout] e72b19aeec770662aab2f674f5efde3f124bd3c98203640625b8b23d00a3a433
Dec 03 01:48:09.125 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-0/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 03 01:48:09.471 INFO [stdout] 2dff6e440976a00c94b5d725e6af869ef4085b3245903d097bc5275af42438fb
Dec 03 01:48:09.473 INFO running `"docker" "start" "-a" "2dff6e440976a00c94b5d725e6af869ef4085b3245903d097bc5275af42438fb"`
Dec 03 01:48:10.143 INFO [stderr] usermod: no changes
Dec 03 01:48:10.180 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 03 01:48:10.180 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 03 01:48:10.180 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 01:48:10.180 INFO [stderr] files will be included as a benchmark target:
Dec 03 01:48:10.180 INFO [stderr] 
Dec 03 01:48:10.180 INFO [stderr] * /source/benches/nbody_raw.rs
Dec 03 01:48:10.180 INFO [stderr] * /source/benches/nbody_uom.rs
Dec 03 01:48:10.180 INFO [stderr] * /source/benches/nbody_metric.rs
Dec 03 01:48:10.181 INFO [stderr] * /source/benches/nbody_dimensioned.rs
Dec 03 01:48:10.181 INFO [stderr] 
Dec 03 01:48:10.181 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 01:48:10.181 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 03 01:48:10.181 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 03 01:48:10.181 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 01:48:10.181 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 01:48:10.181 INFO [stderr] 
Dec 03 01:48:10.181 INFO [stderr] For more information on this warning you can consult
Dec 03 01:48:10.181 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 01:48:10.194 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Dec 03 01:48:10.215 INFO [stderr]      Running /target/debug/deps/metric-f00447a8770a0e2d
Dec 03 01:48:10.215 INFO [stdout] 
Dec 03 01:48:10.215 INFO [stderr]    Doc-tests metric
Dec 03 01:48:10.215 INFO [stdout] running 0 tests
Dec 03 01:48:10.215 INFO [stdout] 
Dec 03 01:48:10.215 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 01:48:10.215 INFO [stdout] 
Dec 03 01:48:11.479 INFO [stdout] 
Dec 03 01:48:11.479 INFO [stdout] running 0 tests
Dec 03 01:48:11.479 INFO [stdout] 
Dec 03 01:48:11.479 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 01:48:11.479 INFO [stdout] 
Dec 03 01:48:11.494 INFO [stderr] su: No module specific data is present
Dec 03 01:48:11.784 INFO running `"docker" "inspect" "2dff6e440976a00c94b5d725e6af869ef4085b3245903d097bc5275af42438fb"`
Dec 03 01:48:11.911 INFO running `"docker" "rm" "-f" "2dff6e440976a00c94b5d725e6af869ef4085b3245903d097bc5275af42438fb"`
Dec 03 01:48:12.063 INFO [stdout] 2dff6e440976a00c94b5d725e6af869ef4085b3245903d097bc5275af42438fb
